@KristinLBradley (question) do you think that there should be a test for this, confirming that it does what we think it does?

I'm not finding other examples of tests for things like this so far. But maybe we should be adding tests? I can ask in the next eng sync, thanks.

Btw, currently we just test that the value of this is not empty. Would it be better to test that it has the default value?

/integration/components/hds/form/key-value-inputs/add-row-button-test.gts

test('it should provide an `aria-description` attribute', async function (assert) {
  await render(
    <template>
      <HdsFormKeyValueInputsAddRowButton
        id="test-form-key-value-add-row-button"
      />
    </template>,
  );
  assert
    .dom('#test-form-key-value-add-row-button')
    .hasAttribute(
      'aria-description',
      /.+/,
      'aria-description should not be empty',
    );
});

I think "not empty" is fine since it can be customized. But you could have another test that ensures the default is the fallback. 🤔

I went ahead and updated the test to instead check for the default value. Please let me know if it looks ok now or if I should change/add anything else. Thanks!

@shleewhite tagging you too just to let you know about the latest update I pushed.